
APAR= II09210
CA400OS2OPT INSTALLATION INFORMATION


 ** Last updated 12/20/96 **


Icon Shadowing Problems with OS/2 Warp Fix Packs
________________________________________________

There is a shadowing problem with some of the Client Access
icons during installation.  The problems originated in Fix
Pack 17 and have been resolved in Fix Pack 26.  The icons
with the problems include:

- Client Access/400 Templates icon
- History Log and Problem Log icons
- Communications Manager and FFST/2 Folder icon

The workaround to the problem is to create the shadows manually.

- The Client Access Templates folder is located in the OS/2
  Templates folder.
- The HISTORY.LOG and PROBLEM.LOG icons can be shadowed by using
  the Graphical Drives program. Open the appropriate drive where
  Client Access is installed and expand the Client Access folder
  (i.e. CAOS2). Open the Service folder to find the icons.
- The Communications Manager and FFST/2 Folders are located on
  the desktop and can be shadowed or moved to the Client
  Access/400 Components folder.

Warp Connect
____________

Client Access/400 Optimized for OS/2 is supported using
the communication features of Warp Connect such as MPTS
and TCPIP, with the following restrictions:

1. If you install MPTS from Warp Connect and your PC is
   connected to the AS/400 via SNA, then the client
   management functions will not work. Client management
   functions require sockets support and thus would need
   to use the ANYNET function to send client management
   data to the AS/400 via sockets over SNA.  However
   there is an incompatibilty with this version of MPTS
   and the ANYNET support we ship with Client Access/400.
   The client management function is turned off, by
   default, and is the only function which will not work.
   All other functions continue to work.

2. Client Access/400 Optimized for OS/2 will not work with
   the Communication Manager/2 (CM/2) SNA Application
   Environment that ships with the OS/2 Warp Connect
   AttachPak.


Coexistence with OS/2 Warp's Internet Access Kit
________________________________________________

The Client Access installation code has been changed
(PTF SF28365) such that if TCPIP is detected on the PC,
the TCPIP component of Client Access (AnyNet) will not
be installed.  This will preserve the configuration of
an installed Internet Access Kit. The TCPIP component
of Client Access Optimized for OS/2 does not contain
all of the function that is needed by the Internet
Access Kit that ships with OS/2 Warp.  The TCPIP that
ships with the Internet Access Kit does not contain all
of the function that is needed by Client Access.  If
TCPIP is the desired communication protocol, then a
full TCPIP product (such as that included in OS/2 Warp
Connect) will be required.  The updated installation code
in this PTF will allow Client Access to co-exist with
the Internet Access Kit provided that SNA is the desired
communication protocol.


Installing on IBM Systems preloaded with WARP
_____________________________________________

When installing Client Access/400 Optimized for OS/2, on
certain IBM PCs that have been preloaded with OS/2 Warp or
systems that have been reinstalled with the Customer Recovery
Pack CD, the installation may fail with rc=X'FE12'.

Check the CAINSTAL.LOG in the OS2 INSTALL directory for the
following message:

  CWBNL0202 - The message file CWBINMSG.DLL could not be found.

In this case, check the following directories to see if the
archive attribute is turned on (all "" should be backslashes):

  OS2
  OS2DLL
  WINDOWS
  WINDOWSSYSTEM

If the archive attributes are turned on, then the problem
can be corrected by turning off the archive attribute for
the affected subdirectories.  Use the following commands at an
OS/2 command prompt (all "" should be backslashes):

  ATTRIB -A OS2
  ATTRIB -A OS2DLL

If the Windows print drivers are to be installed, the following
commands must also be used (all "" should be backslashes):

  ATTRIB -A WINDOWS
  ATTRIB -A WINDOWSSYSTEM


Previous version of UPM
_______________________

If you have an older version of User Profile Management
(UPM), the following warning may occur during Client Access
install.

  Communications Manager is unable to update IBMLVL.INI.
  This file is used by other applications that cannot
  function correctly unless IBMLVL.INI is updated.

This should not impact the installation of Client Access.

CWBUI0152 and CWBUI0193 Messages
________________________________

If any of the following error messages occur during
installation:

  CWBUI0152 - Failed to save the configuration changes to
              Communication Manager.
  CWBUI0193 - Error code 9 occurred interfacing with
              Communication Manager.

Check the CMRINST.LOG file located in the CMLIB directory.
This log file contains detailed information about the error.
If the CMRINST.LOG indicates you have an old version of UPM,
then delete the MUGLIB directory and retry Client Access
installation again, starting with part 1.

If you use a lan server drive for temporary files, you may
also see these errors.  Specifically, CWBUI0193 with error
code 8 followed by CWBUI0191 error code 4.  If this occurs,
edit your CM.INI file located in the CMLIB directory.  You
should see a statement like this:

    CMSource=x: CWB$TEMP COMM-MGR

  where x: is the temporary lan drive.

This problem can be fixed in one of two ways:
  1) Change the x: to a drive that is always available,
     like a local drive on your PC.  The path does not
     have to exist on the local drive.
  2) Make sure x: is available when you configure Client
     Access.


Unsupported adapter in DBCS
___________________________

The Enhanced 5250 Emulation Adapter (ISA bus) is not
supported on DBCS versions of OS/2.  If this adapter is
selected, Client Access install part 1 will fail and the
CAINSTAL.LOG will contain a message indicating that the
value specified for the adapter type is invalid.

The Microchannel twinaxial adapter is referred to as a
5250/A adapter but in order to configure that adapter
during the Client Access install, the IBM System 36/38
Workstation Emulation Adapter/A must be selected (the
first adapter in the list of twinaxial adapters in Client
Access install).  The Enhanced 5250 Emulation Adapter/A is
not supported on OS/2-J.


Rumba Communication Console
___________________________

Some National Language versions of the Rumba Communication
Console may fail to install correctly.  The message that
appears in the CWBRMERR.LOG is - "Error:  Could not copy
file from C:CON$TEMPMRI2924RUMBAWSF.MWF to
C:RMBAOS2MRI2924RUMBAWSF.MWF with rc = 3".  If this
error occurs, you must set the EHNL environment variable to
the National Language Feature code of the installation
diskettes.  After setting the the EHNL environment
variable, the install can be attempted again.  The
following is an example of the statement that must be
entered in the CONFIG.SYS file for the German National
Language Feature.  Also, note that a reboot is needed.

  SET EHNL=2929


VPD.INI File Corruption
_______________________

Client Access/400 Part 1 installation may fail with return
code 'FF08'.  Check the CAINSTAL.LOG located in the
OS2INSTALL directory for the following error:

-------------------------------------------------------------
11   -   Installation Processing            11:06:25 AM
An error occurred setting FFST/2 options.  The FFST/2 file
D:OS2VPD.INI be corrupted.
CCD0019: Response file processing ended with return code 3072.
-------------------------------------------------------------

To correct the problem, verify where the VPD.INI is located.  In
most cases the VPD.INI file is located in the OS2 directory of
the OS/2 boot drive.  In some rare cases this file may be in the
root directory of the boot drive or you may not have a VPD.INI
file.  The VPD.INI file MUST be located in the OS2 directory
in order for Client Access to install correctly.  Follow these
steps to correct or recreate the VPD.INI file.

  - Open an OS/2 window and change directory to OS2

  - Make a backup copy of the corrupted VPD.INI file, if you
    have one.  For example, "copy VPD.INI VPD.BAK".

  - Run the program EPWCONS from the OS/2 command line and do
    the following steps:
     -- Select Options from the menu bar
     -- Select Hardware information...
     -- Press OK
     -- Select Options from the menu bar again
     -- Select Configuration...
     -- Press OK
     -- You may get the follow message popup:
        "For configuration changes to become effective,
        turn FFST/2 off then on again."
        Press OK
     -- Close the Message Console window.  This will rebuild the
        VPD.INI file.  Make sure the VPD.INI file is located in
        the OS2 directory.  If the VPD.INI file was created in
        the root directory copy it to the OS2 directory.  Also,
        check the date and time on the VPD.INI file to verify
        that it was updated.

  - Restart Client Access/400 part 1 installation.

** NOTE ** Due to a problem with backslashes not printing
correctly in this file, please change all vertical bars ""
to backslashes.


